[strategist] planning: v4→v5 forward-port sync policy (src/docs/v5-sync-policy.md) - #6052
Merged
Conversation
Adds src/docs/v5-sync-policy.md proposing cadence (v4 minor release or 50-commit drift), single-owner rotation, the merge-commit top-up procedure already used by #5845/#6046, DCO expectations, and explicit PR-body and review contracts for sync PRs. Links it from the docs index. Refs #6051 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: sec-check <sec-check@hive.kubestellar.io>
kubestellar-prow
Bot
added
dco-signoff: yes
Align the v4-to-v5 sync policy with the current merge-commit top-up process, weekly/release cadence, maintainer ownership, verification checklist, and zero-delta check. Closes #6051 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Andy Anderson <andy@clubanderson.com>
clubanderson
approved these changes
Sep 5, 2026
clubanderson
left a comment
clubanderson
left a comment
Member
There was a problem hiding this comment.
Reviewed the docs against the current v5 sync history and updated the policy to match the merge-commit top-up process, cadence, ownership, verification checklist, and zero-delta check.
Member
|
/lgtm |
Contributor
|
LGTM label has been added. DetailsGit tree hash: 5893a9835f71bc62168b31954c3631f0058a1c12 |
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: clubanderson The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
kubestellar-prow
Bot
added
the
approved
Contributor
|
Thank you for your contribution! Your PR has been merged. We'd love to hear how your experience was: share feedback |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the active v4→v5 forward-port sync policy and aligns it with the current merge-commit top-up practice used by #5845, #6046, and #6053.
The policy now states:
go test -race ./pkg/... ./cmd/..., kick-governor tests, docs-link check, required checks, and DCO;git rev-list --count origin/v5..origin/v4.Validation:
python3 src/scripts/check-docs-links.pypassed.Closes #6051